home *** CD-ROM | disk | FTP | other *** search
- Path: oxy.rust.net!usenet
- From: pgunn@mail.cbf.com (Paul Gunn)
- Newsgroups: comp.lang.c++
- Subject: Re: Constructor Exceptions
- Date: Tue, 09 Jan 1996 13:26:09 GMT
- Organization: Rust Net - High Speed Internet in Detroit 810-642-2276
- Message-ID: <4ctqho$cl7@oxy.rust.net>
- References: <4bud9g$pv5@oxy.rust.net> <4cbhcl$kst@dawn.mmm.com> <4ce68n$8u4@sundog.tiac.net> <4ch1c3$bsm@oxy.rust.net> <4cqjps$337@dub-news-svc-1.compuserve.com>
- NNTP-Posting-Host: pgunn.cbf.com
- X-Newsreader: Forte Agent .99c/32.126
-
- 100754.2730@compuserve.com (Martin Aupperle) wrote:
-
-
- >Visual C++ 2.1 does not implement exception handling as part of the
- >language. Instead, you use macros that translate into a simulation. If
- >I remember right, constructors are not the only area where that
- >mechanism does not work correctly. Stack unwinding and destroying
- >already created subobjects do not work either. Also, you have to
- >derive your exception classes from a certain base class.
-
- That is true of the MFC exceptions in VC 1.x. However, 2.x does
- support ansi draft exceptions. The question is whether there are
- Microsoft - specific limitations built in.
-
-
-